-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: log form updates #2063
feat: log form updates #2063
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
our logging setup is complicated enough as is - I think you should extend loggingMiddleware
's dynamicMeta
function in logging.ts
instead.
Bonus points if you can spot quick refactors at the same time.
@liangyuanruo thoughts for your consideration logging it via loggingMiddleware would capture body data from all requests - even submission responses, which we don't want to store in logs We could set a condition to log the body only if the url corresponds to an admin form route, but then isn't it neater to do it at the admin form router level? |
I agree w this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, agree with you and Antariksh. will approve first
@mantariksh thanks for reviewing, pls see if proposed logging of query params is ok |
Co-authored-by: Antariksh Mahajan <[email protected]>
thanks @mantariksh :) |
Problem
Closes #2056
Tests
body
meta.